Limitations and considerations

The following limitations apply when using Google Cloud BigQuery as a target in a Replicate task:

• The following DDLs are not supported:
  • Drop column
  • Rename column
  • Change column data type
  • Rename table
• Files will be loaded to BigQuery uncompressed and unencrypted.
• The Transactional Apply Change Processing Mode is not supported.
• The Allow unlimited LOB size LOB handling option is not supported.

• Capturing changes from source tables without a Primary Key or Unique Index is not supported. If you need to capture changes from such tables, you can add a Primary Key using a transformation. Additionally, Primary Key or Unique Index columns cannot contain NULLs. If you are aware that such columns will be populated with NULL values, define a transformation to change the NULLs to non-nullable values.

• The Log record to the exceptions table error handling option for Apply Conflicts and Data Errors is not supported.

• With the following task settings configuration, Replicate will perform a DELETE operation followed by an INSERT operation when an UPDATE is encountered:

  • Change Processing Mode is set to Batch optimized apply

  • The Apply changes using SQL MERGE option is not selected

  • The Apply Conflicts error handling for UPDATEs is set to: No record found for applying an UPDATE: INSERT the missing target record

  As Google Cloud BigQuery does not support rollback, in the event that Replicate is unable to insert the updated row, the data will be deleted from the target.